-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-29112][YARN] Expose more details when ApplicationMaster reporter faces a fatal exception #25810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…er faces a fatal exception
|
@jerryshao Could you have a time to review? |
|
ok to test |
|
Test build #110741 has finished for PR 25810 at commit
|
|
add to whitelist |
|
retest this please |
|
Test build #110766 has finished for PR 25810 at commit
|
|
Test build #110763 has finished for PR 25810 at commit
|
jerryshao
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
|
Jenkins, retest this please. |
|
Test build #110856 has finished for PR 25810 at commit
|
|
LGTM, merging to master branch. |
What changes were proposed in this pull request?
In
ApplicationMaster.Reporterthread, fatal exception information is swallowed. It's better to expose it.We found our thrift server was shutdown due to a fatal exception but no useful information from log.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manual test